When an application has a new version or new features, users can use Kubernetes’ rolling update feature to upgrade. Rolling updates allow older versions of application pods to be gradually replaced with new pods without affecting overall service availability, so that even if there are issues with the new version, you can quickly roll back to a stable version. Users can set the number of upgrade steps and waiting time to control the speed and risk of the upgrade process.

When a new version of an application image is released on Docker Hub, you can upgrade your workloads running a previous version to a new one.

Note:

Updating workload deployment and policy may result in the pods recreation, user’s access and application performance will be got impacted during recreation. For example, changing the parameters of the spec.template of a pod, adjusting the resource requests, or modifying the settings of pod affinity/node selector will lead to the deletion of an existing pod and the creation of a new one.

Procedure

1. Go to EonKube > Advanced > Workloads.
2. On the left panel, select the workload type.
3. Find the workload that you want to upgrade. Click ⋮ icon at the end of the row and click Edit Con-fig option.
4. On the mid panel, click container-0.
5. Update the container image.
6. On the mid panel, click Pod.
7. Review and edit the workload's Scaling and Upgrade Policy.
8. On the mid panel, click Deployment.
9. Review and edit the workload's Scaling and Upgrade Policy.
10. Click Save.